Skip to content

Conversation

zanmato
Copy link
Collaborator

@zanmato zanmato commented Apr 25, 2025

This adds key and meta to the route context, and re-exports the beforeEach routing handlers from $app/index to allow the developer to override these methods.
Also adds an i18n example (vue-i18n) that has both locale prefix and domain routing, by overriding the above methods and properties.

Checklist

Copy link

netlify bot commented Apr 25, 2025

Deploy Preview for agitated-mahavira-26f8f9 ready!

Name Link
🔨 Latest commit eb7fd40
🔍 Latest deploy log https://app.netlify.com/projects/agitated-mahavira-26f8f9/deploys/689b02ca6a0ff400081fdfde
😎 Deploy Preview https://deploy-preview-244--agitated-mahavira-26f8f9.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@zanmato
Copy link
Collaborator Author

zanmato commented Apr 25, 2025

@galvez I think this is a better approach, see the first commit for the changes to the vue package, and the second commit on how I've overridden the routing creation to enable i18n routing. The routing file is a bit verbose, but I don't think we could shorten it that much to be honest

@galvez galvez self-requested a review April 26, 2025 02:44
@galvez galvez self-assigned this Apr 29, 2025
zanmato added 2 commits May 2, 2025 15:39
This allows the developer to use their own key for the routeMap matching, as well as
provide meta data per route.
This also re-exports beforeEach handlers, so that they can be overridden in the virtual files.
This example overrides $app/index.js and provides new route creation as well as
beforeEach handlers to enable locale prefix and domain routing.
@zanmato zanmato force-pushed the feature-modular-i18n branch from 73ac965 to e0a449b Compare May 2, 2025 13:42
This confuses vite's build import analysis
Copy link

changeset-bot bot commented Aug 12, 2025

⚠️ No Changeset found

Latest commit: eb7fd40

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants